So, welcome back to Software Engineering.

And today I'm actually traveling.

I'm here in Weichenfeld in Franconia, Switzerland.

So therefore we have to record using Zoom and also broadcast.

So I'm very unfortunate that I can't be there.

But this doesn't hold us back to talk a little bit about software engineering.

Today we want to look into software project management.

So this is really a crucial topic because it essentially brings everything together that we talked about so far.

So we have the requirements engineering.

We looked at how to design a software from an architectural point of view,

then how to go down and really use design patterns in individual class designs and so on.

We talked about testing.

We talked about then also how to plan the deployment and so on.

And today we want to look into the actual project management.

So here the topics will be, first of all, we want to introduce what is software project management.

We will learn about a couple of things that are tremendously useful.

And in particular, in your studies, you will at some point have project works.

And there all the things that we talk about today will kind of be important.

We will go into a little bit more detail and more detailed estimates of time and cost management,

which you probably will only need if you're really doing this with an industrial background.

So if you're in a company, but of course, many of those things will be very relevant for you in your working environment

to understand how the projects are set up and what your manager is thinking about.

If you're also thinking about going into a management direction, you should know about those points as well.

So we will cover then also quality management, human resource management.

So what is important in a team, what can go wrong in a team and what is a good configuration for a team.

And we talk about also risk management.

All right, let's start with what is software project management.

Now, software project management is essential to keep essentially everything under control.

And the software is delivered on time, that we are keeping the budget, that we also meet the customer's expectation

and we remain a coherent and well-functioning development team.

So we have to bring all of the points together.

So we don't want to have only the processes, but it's also about people working together and estimates and how well they can work together.

And this is done in the project management.

Unfortunately, good project management cannot guarantee a successful outcome.

So if you have very good managers, this doesn't mean that the project will always be successful.

There can be technical risks. There can be also other risks.

You know, if your company goes bankrupt, then the team working on a specific project,

they might also have to stop, although they did very good project management.

On the other hand, however, if you have bad project management, then that usually leads to a project failure.

And we will see what kind of bad management can actually happen.

And also, we will see that some of those management textbooks also work.

I found that a little bit surprising how they are spelling out some things that people would think that are very, very common sensical.

But apparently, you have to talk about these things because some managers apparently need to learn about these things.

So you will see that is quite interesting if you look into management textbooks.

So obviously, a couple of different difficulties that is a little bit different in software project management compared to like regular project management.

The software project is intangible, so you cannot touch it.

It's not a chair. It's not manufactured in a way like you would manufacture a car.

So the project manager must rely on others to review the progress.

So this is sometimes difficult.

And in particular, the project manager should have a good understanding about the processes and about software himself.